Skip to content

[release-4.15] OCPBUGS-78171: hermetic 4.15#164

Open
fgallott wants to merge 2 commits intoopenshift:release-4.15from
fgallott:hermetic-4.15
Open

[release-4.15] OCPBUGS-78171: hermetic 4.15#164
fgallott wants to merge 2 commits intoopenshift:release-4.15from
fgallott:hermetic-4.15

Conversation

@fgallott
Copy link

@fgallott fgallott commented Mar 4, 2026

same as #162

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 4, 2026
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Mar 4, 2026

@fgallott: This pull request explicitly references no jira issue.

Details

In response to this:

same as #162

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@fgallott
Copy link
Author

fgallott commented Mar 10, 2026

/jira cherrypick OCPBUGS-78170

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Mar 10, 2026

@fgallott: Jira Issue OCPBUGS-78170 has been cloned as Jira Issue OCPBUGS-78171. Will retitle bug to link to clone.
/retitle OCPBUGS-78171: [release-4.15] NO-JIRA: hermetic 4.15

Details

In response to this:

/jira cherrypick OCPBUGS-78170

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot changed the title [release-4.15] NO-JIRA: hermetic 4.15 OCPBUGS-78171: [release-4.15] NO-JIRA: hermetic 4.15 Mar 10, 2026
@openshift-ci-robot openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Mar 10, 2026
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Mar 10, 2026

@fgallott: This pull request references Jira Issue OCPBUGS-78171, which is invalid:

  • expected dependent Jira Issue OCPBUGS-78170 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is New instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

same as #162

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@fgallott fgallott changed the title OCPBUGS-78171: [release-4.15] NO-JIRA: hermetic 4.15 [release-4.15] OCPBUGS-78171: hermetic 4.15 Mar 10, 2026
@fgallott
Copy link
Author

fgallott commented Mar 10, 2026

/retest-required

@fgallott
fix for tests
69b0793 
rh-pre-commit.version: 2.3.2
rh-pre-commit.check-secrets: ENABLED
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 13, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: fgallott
Once this PR has been reviewed and has the lgtm label, please assign damdo for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 13, 2026

@fgallott: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-openstack 69b0793 link true /test e2e-openstack

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@fgallott @openshift-ci-robot